Skip to content

Instantly share code, notes, and snippets.

LLM Wiki

A pattern for building personal knowledge bases using LLMs.

This is an idea file, it is designed to be copy pasted to your own LLM Agent (e.g. OpenAI Codex, Claude Code, OpenCode / Pi, or etc.). Its goal is to communicate the high level idea, but your agent will build out the specifics in collaboration with you.

The core idea

Most people's experience with LLMs and documents looks like RAG: you upload a collection of files, the LLM retrieves relevant chunks at query time, and generates an answer. This works, but the LLM is rediscovering knowledge from scratch on every question. There's no accumulation. Ask a subtle question that requires synthesizing five documents, and the LLM has to find and piece together the relevant fragments every time. Nothing is built up. NotebookLM, ChatGPT file uploads, and most RAG systems work this way.

@DaleSeo
DaleSeo / the-no-ai-slop-manifesto.md
Created November 13, 2026 23:12 — forked from dexhorthy/the-no-ai-slop-manifesto.md
No AI Slop 선언문 (비공식 한국어 번역)

No AI Slop 선언문

이 글은 No AI Slop: A Manifesto의 비공식 한국어 번역입니다. 원문과 서명자 명단은 원문 사이트와 원문 Gist에서 볼 수 있습니다.

AIE Code Summit 2026의 발표자와 참가자들이 함께 씀

2001년, 17명의 소프트웨어 엔지니어와 리더가 유타주 스노버드의 스키 산장에 모였다. 당시의 가장 큰 과제였던 무겁고 문서 중심적인 소프트웨어 개발 프로세스를 이해하기 위해서였다.

그 자리에서 애자일 선언문이 나왔다. 네 가지 가치와 열두 가지 원칙은 업계 대부분이 소프트웨어를 만드는 방식을 바꾸어 놓았다.

@dexhorthy
dexhorthy / the-no-ai-slop-manifesto.md
Last active November 16, 2026 00:01
The No AI Slop Manifesto

No AI Slop: A Manifesto

Written by the speakers and attendees of AIE Code Summit 2026

In 2001, 17 software engineers and leaders got together at a ski lodge in Snowbird, Utah to understand the biggest challenge of their time: heavyweight, documentation-driven software development processes.

Out of this we got the Agile Manifesto, four values and twelve principles that changed how most of the industry builds software.

Today we convene to build our own manifesto - the No AI Slop manifesto.

@cmgriffing
cmgriffing / gist:8a3fc8dac96a5436d58126f6f00d8d06
Created November 15, 2026 23:52
Auto-clipper prompt doc
# Autoclip Local rebuild guide
Version 1 · 16 November 2026 · Working application version 0.1.0
Autoclip Local turns a downloaded stream VOD into a shortlist of editable, branded vertical clips. The streamer supplies an editorial brief, reviews the suggestions, adjusts framing and timing, and exports approved clips. Video processing runs locally using Node.js, FFmpeg, and Remotion.
This guide preserves the product decisions and implementation details that made the current app useful. The accompanying kit contains the actual source, dependency lockfile, tests, and selected UI screenshots. Use that source to restore the app when possible; use this specification to reconstruct it when the source is unavailable. This is an application backup, not a backup of the streamer's projects or videos.
## Prompt for a future chat
@loggedbytucker-blip
loggedbytucker-blip / pi-commands.md
Last active November 15, 2026 23:45
Raspberry Pi 5 media server — Immich + Jellyfin + Tailscale

Raspberry Pi 5 Media Server — Commands

Immich (photos) + Jellyfin (movies/TV) + Tailscale (access from anywhere). Commands only, in the order they're run in the video.

Tested August 2026 on:

Hardware Raspberry Pi 5, 8GB — CanaKit Starter Kit PRO
@dixneuf19
dixneuf19 / zsh-virtualenv-setup.md
Last active November 15, 2026 23:44 — forked from hminnovation/zsh-virtualenv-setup.md
Setup python, pip, virtualenv and virtualwrapper, with zsh on a new machine
@jhol-byte
jhol-byte / Ikea_bilresa_scroll_wheel.yaml
Last active November 15, 2026 23:40
Home Assistent Blueprint "Ikea_bilresa_scroll_wheel"
blueprint:
name: Ikea_bilresa_scroll_wheel
description: |
Blueprint for Ikea Bilresa Matter (button and scroll wheel for 3 different channels)
Version: 2026-04-06
Info: https://community.home-assistant.io/t/ikea-bilresa-scroll-wheel-blueprint-matter/965365
domain: automation
# input selectors
input:

Design Thinking

X → Graph → Effect<A, E, R>
│              │   │  │  │
│              │   │  │  └─ what each node needs     (§5)
│              │   │  └──── where the graph breaks   (§4)
│              │   └─────── what flows through nodes  (§2)
│              │
│ └─ nodes = functions, edges = data flow